Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70a45c7c11dbde581ebfceebee2849f11048f3d3a55e4eebb46e00fca2c307c5

Tx prefix hash: fb4d2040cf83dc3892c029b448c1c45cba1e0a93b0ced460bb1eaad7dd28bdf6
Tx public key: 7885253afbf3cfef860b34ebb2564c38ea23c6fea75cfc55c3f8457c1d36fcc8
Timestamp: 1735771067 Timestamp [UCT]: 2025-01-01 22:37:47 Age [y:d:h:m:s]: 01:022:20:34:14
Block: 1188167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274640 RingCT/type: yes/0
Extra: 017885253afbf3cfef860b34ebb2564c38ea23c6fea75cfc55c3f8457c1d36fcc8021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f56f3111d7b7e0681eda15f190e508f619e31c0b5643d121557612cfbf6b1b57 0.600000000000 1674668 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": 1188177, "vin": [ { "gen": { "height": 1188167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f56f3111d7b7e0681eda15f190e508f619e31c0b5643d121557612cfbf6b1b57" } } ], "extra": [ 1, 120, 133, 37, 58, 251, 243, 207, 239, 134, 11, 52, 235, 178, 86, 76, 56, 234, 35, 198, 254, 167, 92, 252, 85, 195, 248, 69, 124, 29, 54, 252, 200, 2, 17, 0, 0, 0, 4, 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