Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b635508897e47c213818f753ddb7096a3c1e6896642d20b686a656af4f93edd4

Tx prefix hash: c312bd9119a3377f6a89d33f67a985dc3111b01e562b0d4451f076d90f825d02
Tx public key: 180a3f4d957d6db05779e6367d2ca14631dedd5ff8efdcbccdf43aa5f17ba912
Timestamp: 1731536321 Timestamp [UCT]: 2024-11-13 22:18:41 Age [y:d:h:m:s]: 00:163:09:46:48
Block: 1153111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116621 RingCT/type: yes/0
Extra: 01180a3f4d957d6db05779e6367d2ca14631dedd5ff8efdcbccdf43aa5f17ba912021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49e8bc88c621198dec8b16885522a662a5d1878a3af7f7a81aa9a3e05e6f559c 0.600000000000 1638718 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": 1153121, "vin": [ { "gen": { "height": 1153111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49e8bc88c621198dec8b16885522a662a5d1878a3af7f7a81aa9a3e05e6f559c" } } ], "extra": [ 1, 24, 10, 63, 77, 149, 125, 109, 176, 87, 121, 230, 54, 125, 44, 161, 70, 49, 222, 221, 95, 248, 239, 220, 188, 205, 244, 58, 165, 241, 123, 169, 18, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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