Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5de44bff6a9265e09be6d78933d7c93f6a77a8d8d7fc7d16866c841980bb48bc

Tx prefix hash: a637e7a93236fc99c47a3f17d74e21c2fd1827f44d5951b2769677ca79a97370
Tx public key: 5bdb4f8abe7ce7a82602a86a1421ff45c60cf8cdcc395ba324d8c919feb9d73a
Timestamp: 1736304357 Timestamp [UCT]: 2025-01-08 02:45:57 Age [y:d:h:m:s]: 00:095:04:59:59
Block: 1192589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67829 RingCT/type: yes/0
Extra: 015bdb4f8abe7ce7a82602a86a1421ff45c60cf8cdcc395ba324d8c919feb9d73a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7141f09cd58945244f456b3859edbd0b783e77f86cf038819bb2ae40a5bdc46 0.600000000000 1679144 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": 1192599, "vin": [ { "gen": { "height": 1192589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7141f09cd58945244f456b3859edbd0b783e77f86cf038819bb2ae40a5bdc46" } } ], "extra": [ 1, 91, 219, 79, 138, 190, 124, 231, 168, 38, 2, 168, 106, 20, 33, 255, 69, 198, 12, 248, 205, 204, 57, 91, 163, 36, 216, 201, 25, 254, 185, 215, 58, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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