Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 634c40a9a4dec52ddba35e9e998b1d0d940b0044b94be9d57f90542eb8ea194c

Tx prefix hash: a00fe817498e32e85c3f8b8b53aa567314b43956f299c74b0a582f17b7df53b8
Tx public key: f5a303abc9e980e09ca83dfd57ffdefb598d3362a06952da7dd7be6c56e3df5a
Timestamp: 1734210283 Timestamp [UCT]: 2024-12-14 21:04:43 Age [y:d:h:m:s]: 00:014:17:20:51
Block: 1175279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10489 RingCT/type: yes/0
Extra: 01f5a303abc9e980e09ca83dfd57ffdefb598d3362a06952da7dd7be6c56e3df5a021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4196a38aa9c76d26abf1dd0c63da6f71d808247e92c0473253e08b92e2d1a91b 0.600000000000 1661536 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": 1175289, "vin": [ { "gen": { "height": 1175279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4196a38aa9c76d26abf1dd0c63da6f71d808247e92c0473253e08b92e2d1a91b" } } ], "extra": [ 1, 245, 163, 3, 171, 201, 233, 128, 224, 156, 168, 61, 253, 87, 255, 222, 251, 89, 141, 51, 98, 160, 105, 82, 218, 125, 215, 190, 108, 86, 227, 223, 90, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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