Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3e370d915851bd8ebfbd9910e0291a949006031efe7f4b2d87104b014caac8a

Tx prefix hash: c816c9c172e559ebc3aa4121a553b3cfa6730753b8dd2ae9a76829652301ff72
Tx public key: 7d5a6be182787cd48dd3a743fbccefb17df1d763a74ac88b66d77078f9b14ae4
Timestamp: 1720388345 Timestamp [UCT]: 2024-07-07 21:39:05 Age [y:d:h:m:s]: 00:277:01:29:19
Block: 1060776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197955 RingCT/type: yes/0
Extra: 017d5a6be182787cd48dd3a743fbccefb17df1d763a74ac88b66d77078f9b14ae4021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9bd6ab2940825480f1ae27ba54510d36a420656dae339fb64c246376e5075ea 0.600000000000 1531261 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": 1060786, "vin": [ { "gen": { "height": 1060776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9bd6ab2940825480f1ae27ba54510d36a420656dae339fb64c246376e5075ea" } } ], "extra": [ 1, 125, 90, 107, 225, 130, 120, 124, 212, 141, 211, 167, 67, 251, 204, 239, 177, 125, 241, 215, 99, 167, 74, 200, 139, 102, 215, 112, 120, 249, 177, 74, 228, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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