Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b8a44f580dc6f49b8fa18786494d6f3de471ed312ca81d613f21b02d550a005

Tx prefix hash: 022e55bf14f74d6663c55140e204c7a33b2f757fd291dcbeaa6d3986c0ca62c2
Tx public key: 2dbeb69e8bef54577da3901b31c96c75e568697f34bfdf5f7beaa35ceb6f9eac
Timestamp: 1729174292 Timestamp [UCT]: 2024-10-17 14:11:32 Age [y:d:h:m:s]: 00:037:15:47:13
Block: 1133617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26873 RingCT/type: yes/0
Extra: 012dbeb69e8bef54577da3901b31c96c75e568697f34bfdf5f7beaa35ceb6f9eac02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0264c9b011de6920ed0b86fda60c97e359ce01bc6177f3cf07e28804afb9bcae 0.600000000000 1616792 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": 1133627, "vin": [ { "gen": { "height": 1133617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0264c9b011de6920ed0b86fda60c97e359ce01bc6177f3cf07e28804afb9bcae" } } ], "extra": [ 1, 45, 190, 182, 158, 139, 239, 84, 87, 125, 163, 144, 27, 49, 201, 108, 117, 229, 104, 105, 127, 52, 191, 223, 95, 123, 234, 163, 92, 235, 111, 158, 172, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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