Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cce3de954f26a934667307a5c8c4442f871c1233a34f05d927a91b0f450f8dbb

Tx prefix hash: c07bcaf7571b9e569797faf18855a34befef160590e84dba2c60abd4affcd9da
Tx public key: 710066e0bfd8888c6cfe4de58defc53696bee8f4de24c002ab2dc0fc3ac6db24
Timestamp: 1578042617 Timestamp [UCT]: 2020-01-03 09:10:17 Age [y:d:h:m:s]: 05:069:16:40:20
Block: 37631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1199737 RingCT/type: yes/0
Extra: 01710066e0bfd8888c6cfe4de58defc53696bee8f4de24c002ab2dc0fc3ac6db2402110000000ed81c26c0000000000000000000

1 output(s) for total of 460.589174994000 dcy

stealth address amount amount idx
00: e8238b2bfe20264eb6d94772d73c2786c197e731775c3e5dafd048444f8ad820 460.589174994000 63974 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": 37641, "vin": [ { "gen": { "height": 37631 } } ], "vout": [ { "amount": 460589174994, "target": { "key": "e8238b2bfe20264eb6d94772d73c2786c197e731775c3e5dafd048444f8ad820" } } ], "extra": [ 1, 113, 0, 102, 224, 191, 216, 136, 140, 108, 254, 77, 229, 141, 239, 197, 54, 150, 190, 232, 244, 222, 36, 192, 2, 171, 45, 192, 252, 58, 198, 219, 36, 2, 17, 0, 0, 0, 14, 216, 28, 38, 192, 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