Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 597f35f15fee1cbd9f9dd139600720ef4e1c7395ee573aeae9b87d80d924eee5

Tx prefix hash: 6c5b518a81d191231eb93ae88d9c5e500cd1dd6845e03e17ec674e85ea2201d0
Tx public key: 98538354baf3faf1c80dfd9d90ad03415e750f74f34d0a1b2a58786f0506b4a3
Timestamp: 1736859559 Timestamp [UCT]: 2025-01-14 12:59:19 Age [y:d:h:m:s]: 00:154:21:22:22
Block: 1197187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110401 RingCT/type: yes/0
Extra: 0198538354baf3faf1c80dfd9d90ad03415e750f74f34d0a1b2a58786f0506b4a30211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8c31c0fba67e2523f2b802df4d459b1f417c69728f1f94eee43a5a3fc0e94d4 0.600000000000 1683794 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": 1197197, "vin": [ { "gen": { "height": 1197187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8c31c0fba67e2523f2b802df4d459b1f417c69728f1f94eee43a5a3fc0e94d4" } } ], "extra": [ 1, 152, 83, 131, 84, 186, 243, 250, 241, 200, 13, 253, 157, 144, 173, 3, 65, 94, 117, 15, 116, 243, 77, 10, 27, 42, 88, 120, 111, 5, 6, 180, 163, 2, 17, 0, 0, 0, 1, 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