Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 878fb1f456511b18be29e1d82c301f53844df1ef117ef389a8ea5a5fc74538b0

Tx prefix hash: f78351770dafd99da3c64e09502b492dd2a0fe708ca85a2d15ffbfa132440b29
Tx public key: 3b992fcae3e2cfa59486efc9fbd16cf2fd3102a647cfd49d69a145a0b6b2458b
Timestamp: 1649655221 Timestamp [UCT]: 2022-04-11 05:33:41 Age [y:d:h:m:s]: 02:218:22:57:57
Block: 477766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 676235 RingCT/type: yes/0
Extra: 013b992fcae3e2cfa59486efc9fbd16cf2fd3102a647cfd49d69a145a0b6b2458b021100000012bf7ee4e7000000000000000000

1 output(s) for total of 16.031093606000 dcy

stealth address amount amount idx
00: 66f97934ead1908c64662a6691a275966f734d513b1bc690227068dd713b2830 16.031093606000 898457 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": 477776, "vin": [ { "gen": { "height": 477766 } } ], "vout": [ { "amount": 16031093606, "target": { "key": "66f97934ead1908c64662a6691a275966f734d513b1bc690227068dd713b2830" } } ], "extra": [ 1, 59, 153, 47, 202, 227, 226, 207, 165, 148, 134, 239, 201, 251, 209, 108, 242, 253, 49, 2, 166, 71, 207, 212, 157, 105, 161, 69, 160, 182, 178, 69, 139, 2, 17, 0, 0, 0, 18, 191, 126, 228, 231, 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