Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a705f2af9a8f9f3c9ab06b2bf25436921a0e7c163703a8fc6e350bcd0233825

Tx prefix hash: 5712a6bae14be57895173b5101a3901ef84d5fd7a53fd3fd61f6e8d417516006
Tx public key: cf0aad92651c1fc2d32611e1c59e2984380ead5e66634f426dde2d0a42f0e734
Timestamp: 1727628901 Timestamp [UCT]: 2024-09-29 16:55:01 Age [y:d:h:m:s]: 00:055:14:37:24
Block: 1120800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39739 RingCT/type: yes/0
Extra: 01cf0aad92651c1fc2d32611e1c59e2984380ead5e66634f426dde2d0a42f0e73402110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e75ecd2d9970206dd2ac2d900abfdc5bb126089ae12ab2f7d67ef390e28dea4 0.600000000000 1602847 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": 1120810, "vin": [ { "gen": { "height": 1120800 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e75ecd2d9970206dd2ac2d900abfdc5bb126089ae12ab2f7d67ef390e28dea4" } } ], "extra": [ 1, 207, 10, 173, 146, 101, 28, 31, 194, 211, 38, 17, 225, 197, 158, 41, 132, 56, 14, 173, 94, 102, 99, 79, 66, 109, 222, 45, 10, 66, 240, 231, 52, 2, 17, 0, 0, 0, 5, 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