Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bad53c9c1037b2e42b0005fb59ee39ef69decc384fe8f76914ee6d98c1ae0ea

Tx prefix hash: 80c408e63a92da520f91e84bd9e91f083069b818d1225422abffc39ecf26f17d
Tx public key: 5eb8e2602976a39c4b995822ebfc75da6f3528facc2fd806938e3a29103a4c1c
Timestamp: 1694502205 Timestamp [UCT]: 2023-09-12 07:03:25 Age [y:d:h:m:s]: 01:209:21:33:17
Block: 846350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411108 RingCT/type: yes/0
Extra: 015eb8e2602976a39c4b995822ebfc75da6f3528facc2fd806938e3a29103a4c1c021100000003faf35c9c000000000000000000

1 output(s) for total of 0.963143893000 dcy

stealth address amount amount idx
00: 870c0c0bf6a34a2268e8655d466bfcf4f5550fe9fa995001eb0ada082d945155 0.963143893000 1299804 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": 846360, "vin": [ { "gen": { "height": 846350 } } ], "vout": [ { "amount": 963143893, "target": { "key": "870c0c0bf6a34a2268e8655d466bfcf4f5550fe9fa995001eb0ada082d945155" } } ], "extra": [ 1, 94, 184, 226, 96, 41, 118, 163, 156, 75, 153, 88, 34, 235, 252, 117, 218, 111, 53, 40, 250, 204, 47, 216, 6, 147, 142, 58, 41, 16, 58, 76, 28, 2, 17, 0, 0, 0, 3, 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