Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f05911a9b777df5988902c3f3f1a9023570233feb73645d784e7a93fb239996f

Tx prefix hash: f44102364903c244cf08869088470b1f1b2168a84cccb0cfa79e2fe05a2e418a
Tx public key: 29033697ba38ee034ea3df106fd92482dd94e1f885e1dc6b26d7e4884b6f0290
Timestamp: 1722374846 Timestamp [UCT]: 2024-07-30 21:27:26 Age [y:d:h:m:s]: 00:249:22:25:26
Block: 1077240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178525 RingCT/type: yes/0
Extra: 0129033697ba38ee034ea3df106fd92482dd94e1f885e1dc6b26d7e4884b6f029002110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dfcf7ebe6034cb4d71b3a2d21db44238646842c34562b0fd9eddb45fc4e2f99 0.600000000000 1549787 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": 1077250, "vin": [ { "gen": { "height": 1077240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dfcf7ebe6034cb4d71b3a2d21db44238646842c34562b0fd9eddb45fc4e2f99" } } ], "extra": [ 1, 41, 3, 54, 151, 186, 56, 238, 3, 78, 163, 223, 16, 111, 217, 36, 130, 221, 148, 225, 248, 133, 225, 220, 107, 38, 215, 228, 136, 75, 111, 2, 144, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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