Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62c7307dda2042d22e04fad072edaa640933f7a889da31a49b497258903a9dc8

Tx prefix hash: 834438beaa939f0e7b0cbcd361e31be8c9915ce6dca2c5e577b81522e95d485c
Tx public key: 8d2f11aad32fe1882698aa00899df052b1a74d8a3e5da93a28a3519c462922e3
Timestamp: 1627729253 Timestamp [UCT]: 2021-07-31 11:00:53 Age [y:d:h:m:s]: 03:288:06:44:57
Block: 304471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 978436 RingCT/type: yes/0
Extra: 018d2f11aad32fe1882698aa00899df052b1a74d8a3e5da93a28a3519c462922e302110000001601f1e57f000000000000000000

1 output(s) for total of 60.139757008000 dcy

stealth address amount amount idx
00: cf2a5605b8ff7fae0eafec676ecbc7de528c571f684fe73e29b2520346753721 60.139757008000 635264 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": 304481, "vin": [ { "gen": { "height": 304471 } } ], "vout": [ { "amount": 60139757008, "target": { "key": "cf2a5605b8ff7fae0eafec676ecbc7de528c571f684fe73e29b2520346753721" } } ], "extra": [ 1, 141, 47, 17, 170, 211, 47, 225, 136, 38, 152, 170, 0, 137, 157, 240, 82, 177, 167, 77, 138, 62, 93, 169, 58, 40, 163, 81, 156, 70, 41, 34, 227, 2, 17, 0, 0, 0, 22, 1, 241, 229, 127, 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