Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d500150eb09344a3ff1c6f06770095bfc481880236ecfe435e0f0414ad71f662

Tx prefix hash: f26f8b04d353e5f7457b32cb2047d79aa19a87f2f986d2d0ab27a70405061fac
Tx public key: 9acad14d84b59eb37ef270c4a862d2f738dfc4ac2be4f39cc14b5fce32ef6ae9
Timestamp: 1734593849 Timestamp [UCT]: 2024-12-19 07:37:29 Age [y:d:h:m:s]: 00:103:03:09:57
Block: 1178455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73463 RingCT/type: yes/0
Extra: 019acad14d84b59eb37ef270c4a862d2f738dfc4ac2be4f39cc14b5fce32ef6ae90211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c13a2247f315eb35ab51c08f72f75e4b0d45c3b979d2c7a4859e9119aec7758 0.600000000000 1664842 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": 1178465, "vin": [ { "gen": { "height": 1178455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c13a2247f315eb35ab51c08f72f75e4b0d45c3b979d2c7a4859e9119aec7758" } } ], "extra": [ 1, 154, 202, 209, 77, 132, 181, 158, 179, 126, 242, 112, 196, 168, 98, 210, 247, 56, 223, 196, 172, 43, 228, 243, 156, 193, 75, 95, 206, 50, 239, 106, 233, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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