Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5c14b3d7d72f39020cb9e958c42f73e5c12e0e94321165525e8a95d1baff8eb

Tx prefix hash: 519e4496687729f079c85fb7aaab53ae9c43fc21c9350310a648a467af55df84
Tx public key: 7b4f7c67461873c9f19af3c8ffba379b1722e286966b158e7c1b6f863685dc51
Timestamp: 1709418002 Timestamp [UCT]: 2024-03-02 22:20:02 Age [y:d:h:m:s]: 01:041:20:38:08
Block: 969829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290931 RingCT/type: yes/0
Extra: 017b4f7c67461873c9f19af3c8ffba379b1722e286966b158e7c1b6f863685dc510211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eabb94eb30a86e5b35366c9ef46b4d0add62a668fd4ee39a26f94104222bf4bf 0.600000000000 1429678 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": 969839, "vin": [ { "gen": { "height": 969829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eabb94eb30a86e5b35366c9ef46b4d0add62a668fd4ee39a26f94104222bf4bf" } } ], "extra": [ 1, 123, 79, 124, 103, 70, 24, 115, 201, 241, 154, 243, 200, 255, 186, 55, 155, 23, 34, 226, 134, 150, 107, 21, 142, 124, 27, 111, 134, 54, 133, 220, 81, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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