Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d54ee6f45a196438c6d34e9d114954379fad9c7c8c942f1c900bc9666f609a5d

Tx prefix hash: 3192114b6e4cdeb26592538c0a09e7f897256f426a569f76391e933ed098186a
Tx public key: 88450913e319d0d26efb534ba63d7f1c78eb0d51fe0ad12852157b7edc8d46b5
Timestamp: 1581255780 Timestamp [UCT]: 2020-02-09 13:43:00 Age [y:d:h:m:s]: 04:334:16:08:29
Block: 61431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1131245 RingCT/type: yes/0
Extra: 0188450913e319d0d26efb534ba63d7f1c78eb0d51fe0ad12852157b7edc8d46b502110000000c12c4732d000000000000000000

1 output(s) for total of 384.108937063000 dcy

stealth address amount amount idx
00: 56a26ee040ece535de4ce9e18db58ff0350ec26c2f28219129954100dd206701 384.108937063000 113213 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": 61441, "vin": [ { "gen": { "height": 61431 } } ], "vout": [ { "amount": 384108937063, "target": { "key": "56a26ee040ece535de4ce9e18db58ff0350ec26c2f28219129954100dd206701" } } ], "extra": [ 1, 136, 69, 9, 19, 227, 25, 208, 210, 110, 251, 83, 75, 166, 61, 127, 28, 120, 235, 13, 81, 254, 10, 209, 40, 82, 21, 123, 126, 220, 141, 70, 181, 2, 17, 0, 0, 0, 12, 18, 196, 115, 45, 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