Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ce9f7de1ef1eea9f189fff9a1275fdfbe38ea5b068a80816526c5621a03ad63

Tx prefix hash: 44ca0a0ec6efd9e1075af42642f98ddd9b2c270d4f4b7640bb4860a4be08681a
Tx public key: 671d10788593a74a272ae14f5a59bbfdecceb6cc0d5a4b830437d642885d0844
Timestamp: 1705017287 Timestamp [UCT]: 2024-01-11 23:54:47 Age [y:d:h:m:s]: 01:069:23:33:34
Block: 933322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311116 RingCT/type: yes/0
Extra: 01671d10788593a74a272ae14f5a59bbfdecceb6cc0d5a4b830437d642885d084402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3839a425cec26ddafba40d032d2227cbf54c1bafd396e8941d9c9d7846581fa 0.600000000000 1391284 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": 933332, "vin": [ { "gen": { "height": 933322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3839a425cec26ddafba40d032d2227cbf54c1bafd396e8941d9c9d7846581fa" } } ], "extra": [ 1, 103, 29, 16, 120, 133, 147, 167, 74, 39, 42, 225, 79, 90, 89, 187, 253, 236, 206, 182, 204, 13, 90, 75, 131, 4, 55, 214, 66, 136, 93, 8, 68, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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