Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cb046e5b61fde85cec5f0a38a9513ee8cf7469ef9470d197ec031322c32120d

Tx prefix hash: 91a07fcc8ddbf72fea1bfc395c150293fa5fce8ae64dd3d7270ddd135edb0f16
Tx public key: b43e89850cf749fc5fb16598de3fc3719b56b93819df7e5df297ea4a98ef9d1c
Timestamp: 1733945146 Timestamp [UCT]: 2024-12-11 19:25:46 Age [y:d:h:m:s]: 00:035:17:25:35
Block: 1173079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25521 RingCT/type: yes/0
Extra: 01b43e89850cf749fc5fb16598de3fc3719b56b93819df7e5df297ea4a98ef9d1c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bb4e8e8fd115591b53a787fc257379de55c336623d01125bafeeeae3e4185c7 0.600000000000 1659058 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": 1173089, "vin": [ { "gen": { "height": 1173079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bb4e8e8fd115591b53a787fc257379de55c336623d01125bafeeeae3e4185c7" } } ], "extra": [ 1, 180, 62, 137, 133, 12, 247, 73, 252, 95, 177, 101, 152, 222, 63, 195, 113, 155, 86, 185, 56, 25, 223, 126, 93, 242, 151, 234, 74, 152, 239, 157, 28, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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