Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08d095fcda67433908e9d6107cc3a0401066ea0068cffc5a4c7860d4e64b2def

Tx prefix hash: ad858ca8d88951d5c5161e7c64ce0c6c0ae955e4bd1bf0b787751443981c2e7c
Tx public key: 9f4f2d134dbc6f3afc5bd0b594f0aae58efddf06b4fa71c4dc34473c5438caee
Timestamp: 1722003633 Timestamp [UCT]: 2024-07-26 14:20:33 Age [y:d:h:m:s]: 00:251:04:27:40
Block: 1074167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179420 RingCT/type: yes/0
Extra: 019f4f2d134dbc6f3afc5bd0b594f0aae58efddf06b4fa71c4dc34473c5438caee021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f45b47f179d3208be16c8390a6194a9f0ab5897b1bfcdf68963fbe085578b241 0.600000000000 1546680 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": 1074177, "vin": [ { "gen": { "height": 1074167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f45b47f179d3208be16c8390a6194a9f0ab5897b1bfcdf68963fbe085578b241" } } ], "extra": [ 1, 159, 79, 45, 19, 77, 188, 111, 58, 252, 91, 208, 181, 148, 240, 170, 229, 142, 253, 223, 6, 180, 250, 113, 196, 220, 52, 71, 60, 84, 56, 202, 238, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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