Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e35b304f8fe377e59bfb83c2f4399ca34d45b4b46e92775f04400de2e94969d

Tx prefix hash: 4b1e6e1dba05415ebe7cc351a83a6f94dbd188b0b05d5ef6830b3e4ced0abec3
Tx public key: e954ef1dd9a3515836b20707fc2ef3dcae4478dd61bad39e6c698cb3e8f72e5c
Timestamp: 1728391994 Timestamp [UCT]: 2024-10-08 12:53:14 Age [y:d:h:m:s]: 01:043:12:38:13
Block: 1127128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289487 RingCT/type: yes/0
Extra: 01e954ef1dd9a3515836b20707fc2ef3dcae4478dd61bad39e6c698cb3e8f72e5c021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0250be3334b5127630e593bca35faee8874d7dd1283dbc8032d817fda0dc3f5 0.600000000000 1609927 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": 1127138, "vin": [ { "gen": { "height": 1127128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0250be3334b5127630e593bca35faee8874d7dd1283dbc8032d817fda0dc3f5" } } ], "extra": [ 1, 233, 84, 239, 29, 217, 163, 81, 88, 54, 178, 7, 7, 252, 46, 243, 220, 174, 68, 120, 221, 97, 186, 211, 158, 108, 105, 140, 179, 232, 247, 46, 92, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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