Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1105c4100e2b84cf59b927ca8f0eaca7179056bc36675815096e299cf8240c50

Tx prefix hash: 328bc11a28fcd093af8fd374327a2c09210bb7622ccb60e3b1136c3d3911f6f9
Tx public key: 6800f6fee4211b93fe1ddd3c86b5f79e995ed361ff3dcb3c3bf114bb60a472b8
Timestamp: 1695975806 Timestamp [UCT]: 2023-09-29 08:23:26 Age [y:d:h:m:s]: 01:202:01:42:38
Block: 858587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405482 RingCT/type: yes/0
Extra: 016800f6fee4211b93fe1ddd3c86b5f79e995ed361ff3dcb3c3bf114bb60a472b8021100000003faf35c9c000000000000000000

1 output(s) for total of 0.877293470000 dcy

stealth address amount amount idx
00: 4635706d46a3df354a56092a22fd37b26d714950b7975e6150669d031987d2d7 0.877293470000 1312769 of 0

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": 858597, "vin": [ { "gen": { "height": 858587 } } ], "vout": [ { "amount": 877293470, "target": { "key": "4635706d46a3df354a56092a22fd37b26d714950b7975e6150669d031987d2d7" } } ], "extra": [ 1, 104, 0, 246, 254, 228, 33, 27, 147, 254, 29, 221, 60, 134, 181, 247, 158, 153, 94, 211, 97, 255, 61, 203, 60, 59, 241, 20, 187, 96, 164, 114, 184, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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