Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50899f384214b648f77379bfb7b727d833f489a42a8e14f1229dc26ce933ba2f

Tx prefix hash: 876b8f46259328a5256003bda611a907c2801334dcb9bcfc53ae52c45a4b9682
Tx public key: 962b64fbfb1bdb4e7dc68109db76868a64a4082b15f192bb99fbb67a2e9fc2a7
Timestamp: 1738008393 Timestamp [UCT]: 2025-01-27 20:06:33 Age [y:d:h:m:s]: 00:045:19:58:50
Block: 1206462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32771 RingCT/type: yes/0
Extra: 01962b64fbfb1bdb4e7dc68109db76868a64a4082b15f192bb99fbb67a2e9fc2a702110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddf5627c2712b432c9e66ba83f56482747e020c2a58a881d1ef82ad21f3fe81e 0.600000000000 1693167 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": 1206472, "vin": [ { "gen": { "height": 1206462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddf5627c2712b432c9e66ba83f56482747e020c2a58a881d1ef82ad21f3fe81e" } } ], "extra": [ 1, 150, 43, 100, 251, 251, 27, 219, 78, 125, 198, 129, 9, 219, 118, 134, 138, 100, 164, 8, 43, 21, 241, 146, 187, 153, 251, 182, 122, 46, 159, 194, 167, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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