Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80c1d47d63f5f438dcff683c1534f2c7097946fce2da04010a3111ca645fa982

Tx prefix hash: 68d06e58331819e6dddd6512b1449dc19d2107927842cc4f8cdd79beee5f746e
Tx public key: 6af992bd509d486bbbc24c5a2863acd9dd9fd9a9411c95d8e46a5468ceb4d03e
Timestamp: 1584527545 Timestamp [UCT]: 2020-03-18 10:32:25 Age [y:d:h:m:s]: 05:233:17:48:40
Block: 84923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1321029 RingCT/type: yes/0
Extra: 016af992bd509d486bbbc24c5a2863acd9dd9fd9a9411c95d8e46a5468ceb4d03e0211000000038e8a0ce2000000000000000000

1 output(s) for total of 321.081756774000 dcy

stealth address amount amount idx
00: c18f8f6d252e5719176f0fb407931c8fad9c04f05fff48112e0a5a9f507e6ea4 321.081756774000 153709 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": 84933, "vin": [ { "gen": { "height": 84923 } } ], "vout": [ { "amount": 321081756774, "target": { "key": "c18f8f6d252e5719176f0fb407931c8fad9c04f05fff48112e0a5a9f507e6ea4" } } ], "extra": [ 1, 106, 249, 146, 189, 80, 157, 72, 107, 187, 194, 76, 90, 40, 99, 172, 217, 221, 159, 217, 169, 65, 28, 149, 216, 228, 106, 84, 104, 206, 180, 208, 62, 2, 17, 0, 0, 0, 3, 142, 138, 12, 226, 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