Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 514e5918a5d5c5578a9d7358e9ca5003359e864fa97fd3f5c78f3483ce9fe8c9

Tx prefix hash: 8ddce80bdf484a398115b40c0f426a2be94a957e8523314bbee05171ce381e2f
Tx public key: 2d46b257cf147c6f21fbb491e045e9f325eeed31dd507b13d9edc32a66c4ec4a
Timestamp: 1731380328 Timestamp [UCT]: 2024-11-12 02:58:48 Age [y:d:h:m:s]: 00:135:23:58:43
Block: 1151805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97029 RingCT/type: yes/0
Extra: 012d46b257cf147c6f21fbb491e045e9f325eeed31dd507b13d9edc32a66c4ec4a021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abbd0f7db5d0e9e756302568a4d2433de77fe4b6b408de218ac06b565756a8ce 0.600000000000 1637388 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": 1151815, "vin": [ { "gen": { "height": 1151805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abbd0f7db5d0e9e756302568a4d2433de77fe4b6b408de218ac06b565756a8ce" } } ], "extra": [ 1, 45, 70, 178, 87, 207, 20, 124, 111, 33, 251, 180, 145, 224, 69, 233, 243, 37, 238, 237, 49, 221, 80, 123, 19, 217, 237, 195, 42, 102, 196, 236, 74, 2, 17, 0, 0, 0, 2, 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