Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5d5030d8c0d480a0ac44746d47f7d3f9040c1b88cab3ab5877ed9ed2223d177

Tx prefix hash: 58e71c7a6177628b6aaa9b1dd6f69af882a30546e7a8beeedcc2871f96adca0b
Tx public key: f2610c30c6fdf98f47615a1a5232bdd84a2a576c4c5db75647445b3593c106a1
Timestamp: 1703516336 Timestamp [UCT]: 2023-12-25 14:58:56 Age [y:d:h:m:s]: 01:175:10:57:41
Block: 920902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 386434 RingCT/type: yes/0
Extra: 01f2610c30c6fdf98f47615a1a5232bdd84a2a576c4c5db75647445b3593c106a102110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a23c943265ba46c8b87bca7d5a56f651bf7ecbd2310ce0fd7598f1b320c44348 0.600000000000 1378586 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": 920912, "vin": [ { "gen": { "height": 920902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a23c943265ba46c8b87bca7d5a56f651bf7ecbd2310ce0fd7598f1b320c44348" } } ], "extra": [ 1, 242, 97, 12, 48, 198, 253, 249, 143, 71, 97, 90, 26, 82, 50, 189, 216, 74, 42, 87, 108, 76, 93, 183, 86, 71, 68, 91, 53, 147, 193, 6, 161, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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