Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec9b005655c4281a4d61a4d09e53641016e4155ea0e3f9b421e381bf4d984543

Tx prefix hash: 877e4db04a6b48fa1135d32440bf8f8366a475068f0c2eabd5c94c84d2662aef
Tx public key: 49aa1b195d15ab267727c630028a74c711800882e8dc5bbed1f49c5729bb4fab
Timestamp: 1703902676 Timestamp [UCT]: 2023-12-30 02:17:56 Age [y:d:h:m:s]: 01:128:20:07:57
Block: 924101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353209 RingCT/type: yes/0
Extra: 0149aa1b195d15ab267727c630028a74c711800882e8dc5bbed1f49c5729bb4fab0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a5112f5fea90a5a929a8cca91836e6e151e613c0139619dd3c7f47e9bc913f4 0.600000000000 1381843 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": 924111, "vin": [ { "gen": { "height": 924101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a5112f5fea90a5a929a8cca91836e6e151e613c0139619dd3c7f47e9bc913f4" } } ], "extra": [ 1, 73, 170, 27, 25, 93, 21, 171, 38, 119, 39, 198, 48, 2, 138, 116, 199, 17, 128, 8, 130, 232, 220, 91, 190, 209, 244, 156, 87, 41, 187, 79, 171, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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