Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 199c8dcc57de70041a1fc5404a07b3023376eb282089291c6eab00212a85f2f4

Tx prefix hash: 57c00505ca5dcc3c3a95fd721bc84c4916b4e5cbd1546b6240f8f92963ca3ca3
Tx public key: a5e9dcec439f62d739f65014cd9a1e606c0be29af8849ca95270ee8d0c0fca94
Timestamp: 1728016718 Timestamp [UCT]: 2024-10-04 04:38:38 Age [y:d:h:m:s]: 00:195:07:10:24
Block: 1124019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139382 RingCT/type: yes/0
Extra: 01a5e9dcec439f62d739f65014cd9a1e606c0be29af8849ca95270ee8d0c0fca9402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aae3b4928fd1caf9063d1140c56e3c90018a39c44b090f3fd3280d4b5b3628f3 0.600000000000 1606580 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": 1124029, "vin": [ { "gen": { "height": 1124019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aae3b4928fd1caf9063d1140c56e3c90018a39c44b090f3fd3280d4b5b3628f3" } } ], "extra": [ 1, 165, 233, 220, 236, 67, 159, 98, 215, 57, 246, 80, 20, 205, 154, 30, 96, 108, 11, 226, 154, 248, 132, 156, 169, 82, 112, 238, 141, 12, 15, 202, 148, 2, 17, 0, 0, 0, 3, 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