Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42368b15f34ec852cb067c3a51d5de9eb94581716546cb1fce5c6934a5261718

Tx prefix hash: a0b32027f326906ccbd3f844feaef1319a7b318b4152de1db50ea4418554dbb1
Tx public key: 7d184b50cab2c39c2972b5d9bd8b5a8905d15608c5665fa69267a4a984087c29
Timestamp: 1737873021 Timestamp [UCT]: 2025-01-26 06:30:21 Age [y:d:h:m:s]: 00:047:19:26:56
Block: 1205530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34000 RingCT/type: yes/0
Extra: 017d184b50cab2c39c2972b5d9bd8b5a8905d15608c5665fa69267a4a984087c2902110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a376650c9b0189fd6e62af108ed260adbc1f30407ecdb59468934a7d873c6a10 0.600000000000 1692227 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": 1205540, "vin": [ { "gen": { "height": 1205530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a376650c9b0189fd6e62af108ed260adbc1f30407ecdb59468934a7d873c6a10" } } ], "extra": [ 1, 125, 24, 75, 80, 202, 178, 195, 156, 41, 114, 181, 217, 189, 139, 90, 137, 5, 209, 86, 8, 197, 102, 95, 166, 146, 103, 164, 169, 132, 8, 124, 41, 2, 17, 0, 0, 0, 10, 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