Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 235f8811dd5dd308656cb065b210c94362aedcf7f13e12fc3d7bc209e4c335e1

Tx prefix hash: 4cfcd630c3037757e55e661e34673947ef937504132b121cba23337bacee1020
Tx public key: 0b1c1a4e23e294b052dd3f3fcaf2291e1d26e6a10fff9d4900cfa160827abf81
Timestamp: 1734340718 Timestamp [UCT]: 2024-12-16 09:18:38 Age [y:d:h:m:s]: 00:180:22:02:32
Block: 1176358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129031 RingCT/type: yes/0
Extra: 010b1c1a4e23e294b052dd3f3fcaf2291e1d26e6a10fff9d4900cfa160827abf810211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72ad1ec26f19d639370f4af9ea27e899b1e1a804e764bbfd68704b737dc01851 0.600000000000 1662689 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": 1176368, "vin": [ { "gen": { "height": 1176358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72ad1ec26f19d639370f4af9ea27e899b1e1a804e764bbfd68704b737dc01851" } } ], "extra": [ 1, 11, 28, 26, 78, 35, 226, 148, 176, 82, 221, 63, 63, 202, 242, 41, 30, 29, 38, 230, 161, 15, 255, 157, 73, 0, 207, 161, 96, 130, 122, 191, 129, 2, 17, 0, 0, 0, 5, 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