Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18a1709cb58ac2c96a09b5fa6ed580f60652a5f33d8a444ae2264d2f77187f9e

Tx prefix hash: 29f442a9f8b46d11d026cbca3fd387e9231cdb9d9fa2c58ba58c29c88ae42860
Tx public key: b3bb866407318d4b3912f660d939db133ccefb28540b78ed150747ece5a0d3ec
Timestamp: 1714748488 Timestamp [UCT]: 2024-05-03 15:01:28 Age [y:d:h:m:s]: 00:141:06:18:22
Block: 1014023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101180 RingCT/type: yes/0
Extra: 01b3bb866407318d4b3912f660d939db133ccefb28540b78ed150747ece5a0d3ec0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9113a4cd5e0012af5a5ad620e445a3d0957f47ec3ad2865a10e9e9e0b6b93981 0.600000000000 1476998 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": 1014033, "vin": [ { "gen": { "height": 1014023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9113a4cd5e0012af5a5ad620e445a3d0957f47ec3ad2865a10e9e9e0b6b93981" } } ], "extra": [ 1, 179, 187, 134, 100, 7, 49, 141, 75, 57, 18, 246, 96, 217, 57, 219, 19, 60, 206, 251, 40, 84, 11, 120, 237, 21, 7, 71, 236, 229, 160, 211, 236, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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