Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fdd0ab678f46e598221b4c3d430c0e8fc3c2054ad7af026704ce87e6d7606ff

Tx prefix hash: b346828345bed530b34d2b29d207d878ad4cbc3de27fbe27f0aacbbb1e5006d0
Tx public key: 8e440ff9adeda6162f29e2505f8abec94722b7fd3f150ce1b219e67b3fa1367c
Timestamp: 1712696242 Timestamp [UCT]: 2024-04-09 20:57:22 Age [y:d:h:m:s]: 01:037:15:06:12
Block: 996981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287893 RingCT/type: yes/0
Extra: 018e440ff9adeda6162f29e2505f8abec94722b7fd3f150ce1b219e67b3fa1367c02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ec8d4834c0981a1522b4d2fc5bf1ea5bf02d87ac6febb1e01132904412d2f30 0.600000000000 1457409 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": 996991, "vin": [ { "gen": { "height": 996981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ec8d4834c0981a1522b4d2fc5bf1ea5bf02d87ac6febb1e01132904412d2f30" } } ], "extra": [ 1, 142, 68, 15, 249, 173, 237, 166, 22, 47, 41, 226, 80, 95, 138, 190, 201, 71, 34, 183, 253, 63, 21, 12, 225, 178, 25, 230, 123, 63, 161, 54, 124, 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