Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 058ce83f2e0b4062e3b648a31afb63591b64499fa51cd15fcc06ac8a606c0f73

Tx prefix hash: 6f52c39a34580fc19861d50cff4eb30b8d7e54ccbe58165e58a3dc3323f2dbd2
Tx public key: 0144ac0fce6a58533584a3a18b8dfdb9d0eaa1976739c0082221a5533dfb1e73
Timestamp: 1723322538 Timestamp [UCT]: 2024-08-10 20:42:18 Age [y:d:h:m:s]: 00:309:07:46:07
Block: 1085106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220901 RingCT/type: yes/0
Extra: 010144ac0fce6a58533584a3a18b8dfdb9d0eaa1976739c0082221a5533dfb1e73021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea1c87645df03afa4a4b72cf0fa1d4d75023ec37429a58013fe00d3eac25d472 0.600000000000 1559607 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": 1085116, "vin": [ { "gen": { "height": 1085106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea1c87645df03afa4a4b72cf0fa1d4d75023ec37429a58013fe00d3eac25d472" } } ], "extra": [ 1, 1, 68, 172, 15, 206, 106, 88, 83, 53, 132, 163, 161, 139, 141, 253, 185, 208, 234, 161, 151, 103, 57, 192, 8, 34, 33, 165, 83, 61, 251, 30, 115, 2, 17, 0, 0, 0, 6, 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