Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 361b0328ae28623976dcea2e33b444cf333673a5daa580b975ad63b0c03f5481

Tx prefix hash: 25c46177fcc59b7c49d3024d09c3ac3e5bc9a758173107e1037377a8b516e852
Tx public key: bc139b9a43d67162c0830eaf2f1dace407d16ddb7f7d5e0d7a9cc1aa334d0d5c
Timestamp: 1703021383 Timestamp [UCT]: 2023-12-19 21:29:43 Age [y:d:h:m:s]: 01:327:10:06:58
Block: 916801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492843 RingCT/type: yes/0
Extra: 01bc139b9a43d67162c0830eaf2f1dace407d16ddb7f7d5e0d7a9cc1aa334d0d5c021100000002e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a321b177a31dc9aa0057a9d44ed5c35ed8ed5444a0506d97e46257355724b3d4 0.600000000000 1374361 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": 916811, "vin": [ { "gen": { "height": 916801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a321b177a31dc9aa0057a9d44ed5c35ed8ed5444a0506d97e46257355724b3d4" } } ], "extra": [ 1, 188, 19, 155, 154, 67, 214, 113, 98, 192, 131, 14, 175, 47, 29, 172, 228, 7, 209, 109, 219, 127, 125, 94, 13, 122, 156, 193, 170, 51, 77, 13, 92, 2, 17, 0, 0, 0, 2, 228, 187, 107, 131, 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