Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3829a6420993e2cf18413a8d0b84e9aa5ff6cb7235ff612506ee7848d95739a1

Tx prefix hash: cf3110a994420d58e2399b9373426814f74878e6ab806047001a947cda86e30a
Tx public key: d94e5b3ab5aec9c03eda0df09cd1ad79d0e8899c6bd301914383b66fe9c686d1
Timestamp: 1702811306 Timestamp [UCT]: 2023-12-17 11:08:26 Age [y:d:h:m:s]: 01:108:23:48:16
Block: 915060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339017 RingCT/type: yes/0
Extra: 01d94e5b3ab5aec9c03eda0df09cd1ad79d0e8899c6bd301914383b66fe9c686d102110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b27e15a7cbd2613aad069e4e862ef3a24d820c12ff030bf8363ce88b1aa04e9 0.600000000000 1372440 of 15

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": 915070, "vin": [ { "gen": { "height": 915060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b27e15a7cbd2613aad069e4e862ef3a24d820c12ff030bf8363ce88b1aa04e9" } } ], "extra": [ 1, 217, 78, 91, 58, 181, 174, 201, 192, 62, 218, 13, 240, 156, 209, 173, 121, 208, 232, 137, 156, 107, 211, 1, 145, 67, 131, 182, 111, 233, 198, 134, 209, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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