Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0f109be90cf4e52920635354f32664705415dc5dd0f2bb38c0ccc9b11d1d6d1

Tx prefix hash: 679e3ecadce9f8b25f1db0f85d1d4c09fb892fb65d2362df3d073388e86f9ac1
Tx public key: 145494dd977a6fa02319b9c0d68c8f18d1087b8780bf3c02a36609c821b3e8af
Timestamp: 1579039784 Timestamp [UCT]: 2020-01-14 22:09:44 Age [y:d:h:m:s]: 05:120:17:39:59
Block: 45634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1236486 RingCT/type: yes/0
Extra: 01145494dd977a6fa02319b9c0d68c8f18d1087b8780bf3c02a36609c821b3e8af021100000007d81c26c0000000000000000000

1 output(s) for total of 433.307747059000 dcy

stealth address amount amount idx
00: 0eabb5d7f11a8735ac0a5dd59561a0fbf5947ae7fc560d19d169af097a8043cc 433.307747059000 83486 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": 45644, "vin": [ { "gen": { "height": 45634 } } ], "vout": [ { "amount": 433307747059, "target": { "key": "0eabb5d7f11a8735ac0a5dd59561a0fbf5947ae7fc560d19d169af097a8043cc" } } ], "extra": [ 1, 20, 84, 148, 221, 151, 122, 111, 160, 35, 25, 185, 192, 214, 140, 143, 24, 209, 8, 123, 135, 128, 191, 60, 2, 163, 102, 9, 200, 33, 179, 232, 175, 2, 17, 0, 0, 0, 7, 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