Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab558065ee7c4385844604af06cb6e99edace3d013a110588ea7c61316156bf8

Tx prefix hash: be2e462f4291d0b07e98071e3d5f9e00b433699a6b8ac7b941ff92af7297f56d
Tx public key: ada9c1c25a671c96b599b71398ee3cef26995dcbd7de77c7a353c079cee3a22c
Timestamp: 1721048496 Timestamp [UCT]: 2024-07-15 13:01:36 Age [y:d:h:m:s]: 00:277:02:39:00
Block: 1066259 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197979 RingCT/type: yes/0
Extra: 01ada9c1c25a671c96b599b71398ee3cef26995dcbd7de77c7a353c079cee3a22c02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a77e884f046c3703fb6786f6a39a58064cb2a89bf09be50461388079eeb8d53c 0.600000000000 1536832 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": 1066269, "vin": [ { "gen": { "height": 1066259 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a77e884f046c3703fb6786f6a39a58064cb2a89bf09be50461388079eeb8d53c" } } ], "extra": [ 1, 173, 169, 193, 194, 90, 103, 28, 150, 181, 153, 183, 19, 152, 238, 60, 239, 38, 153, 93, 203, 215, 222, 119, 199, 163, 83, 192, 121, 206, 227, 162, 44, 2, 17, 0, 0, 0, 1, 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