Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93ae8ce574c69d2f887ef1b0b0007279bfa33aa04682a100c55eaf8ac894337b

Tx prefix hash: fd717f5b0269c5a0d4e663604ca9adb02d736961ceb2730b85c418b806bc97cc
Tx public key: f2a8e98a6ed7b999e84ba7e1d4e41d5124499c7af7b1fa7089d81c102bf7a16e
Timestamp: 1720128244 Timestamp [UCT]: 2024-07-04 21:24:04 Age [y:d:h:m:s]: 00:318:04:28:47
Block: 1058608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227382 RingCT/type: yes/0
Extra: 01f2a8e98a6ed7b999e84ba7e1d4e41d5124499c7af7b1fa7089d81c102bf7a16e0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d282193307fa9ae40a343e1be8a5f8d348c6b8f79ea6fdd36274facbee346ebf 0.600000000000 1529065 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": 1058618, "vin": [ { "gen": { "height": 1058608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d282193307fa9ae40a343e1be8a5f8d348c6b8f79ea6fdd36274facbee346ebf" } } ], "extra": [ 1, 242, 168, 233, 138, 110, 215, 185, 153, 232, 75, 167, 225, 212, 228, 29, 81, 36, 73, 156, 122, 247, 177, 250, 112, 137, 216, 28, 16, 43, 247, 161, 110, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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