Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0b139c5d0a2af4323e6de8c0ce061086946f73ab8c3c96782635ae9bfbfe3aa

Tx prefix hash: a0c96bbb236fcb616652191f621d4be3fa86b9fa75963298e7056235acf31546
Tx public key: 7d64a99ed19a1a1c1da441cec641c1b4e76113c57728ec162e7df8a3a214f3fb
Timestamp: 1651776177 Timestamp [UCT]: 2022-05-05 18:42:57 Age [y:d:h:m:s]: 02:208:21:01:40
Block: 494997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 669366 RingCT/type: yes/0
Extra: 017d64a99ed19a1a1c1da441cec641c1b4e76113c57728ec162e7df8a3a214f3fb02110000000afaf35c9c000000000000000000

1 output(s) for total of 14.056256345000 dcy

stealth address amount amount idx
00: a7a2e797e586513bfe304f4ef8185c231014b96d4fdaed000fea004eb0f921cd 14.056256345000 918736 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": 495007, "vin": [ { "gen": { "height": 494997 } } ], "vout": [ { "amount": 14056256345, "target": { "key": "a7a2e797e586513bfe304f4ef8185c231014b96d4fdaed000fea004eb0f921cd" } } ], "extra": [ 1, 125, 100, 169, 158, 209, 154, 26, 28, 29, 164, 65, 206, 198, 65, 193, 180, 231, 97, 19, 197, 119, 40, 236, 22, 46, 125, 248, 163, 162, 20, 243, 251, 2, 17, 0, 0, 0, 10, 250, 243, 92, 156, 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