Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1422ef5e2b603e1eafd53656b5000bf2b1775101338a09d9ad1b8f309a178469

Tx prefix hash: 82c6d3e2abefe15bbdadeab0e823ad799c85199984c0b1371d97d37c3dba1ac2
Tx public key: bd50d1bf6adfe93c3b6d1e4969f70cd37d9d17c84b438822b4c89434b89b8f4a
Timestamp: 1733975668 Timestamp [UCT]: 2024-12-12 03:54:28 Age [y:d:h:m:s]: 00:134:10:24:09
Block: 1173332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95878 RingCT/type: yes/0
Extra: 01bd50d1bf6adfe93c3b6d1e4969f70cd37d9d17c84b438822b4c89434b89b8f4a021100000001a2d75f44000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0660f74757cb803bad4139d96fb25b616de07463401a4db44d867f28bb47290e 0.600000000000 1659343 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": 1173342, "vin": [ { "gen": { "height": 1173332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0660f74757cb803bad4139d96fb25b616de07463401a4db44d867f28bb47290e" } } ], "extra": [ 1, 189, 80, 209, 191, 106, 223, 233, 60, 59, 109, 30, 73, 105, 247, 12, 211, 125, 157, 23, 200, 75, 67, 136, 34, 180, 200, 148, 52, 184, 155, 143, 74, 2, 17, 0, 0, 0, 1, 162, 215, 95, 68, 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