Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 7ce0c7887a30abe4d40fc4e6094dcd56bee3dff6543f360baa2bb38f6d78e2a0

Tx prefix hash: 6dda18b5f7b80be9192113b73601f7b8d248d5729418782a723c58ef2f581c89
Tx public key: fd233f97324770afe7b011c25b1852b3e4ba8ca271a268a42ce0865d5bad160e
Timestamp: 1697275639 Timestamp [UCT]: 2023-10-14 09:27:19 Age [y:d:h:m:s]: 01:177:03:21:21
Block: 869361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387622 RingCT/type: yes/0
Extra: 01fd233f97324770afe7b011c25b1852b3e4ba8ca271a268a42ce0865d5bad160e02110000000333af99f4000000000000000000

1 output(s) for total of 0.808064721000 dcy

stealth address amount amount idx
00: d9dcf08427a602a6ae507aa62c7f29f6293768d19f4c36023be1e14c525fbedc 0.808064721000 1324206 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 869371, "vin": [ { "gen": { "height": 869361 } } ], "vout": [ { "amount": 808064721, "target": { "key": "d9dcf08427a602a6ae507aa62c7f29f6293768d19f4c36023be1e14c525fbedc" } } ], "extra": [ 1, 253, 35, 63, 151, 50, 71, 112, 175, 231, 176, 17, 194, 91, 24, 82, 179, 228, 186, 140, 162, 113, 162, 104, 164, 44, 224, 134, 93, 91, 173, 22, 14, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8