Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc5d7c4b89f231a3f0b160caf44fe642e5639c6ce1f04a143a55321daf4a87e8

Tx prefix hash: c539d3e370ea9d22b81359b68c9a0f59981075425d554b364fd35d47e498ff7e
Tx public key: 88c8c3e3f94310d8c22f3f91ddddd9d51de24eb4c64385ac5d4bf2f848bca69c
Timestamp: 1696575621 Timestamp [UCT]: 2023-10-06 07:00:21 Age [y:d:h:m:s]: 01:050:15:37:44
Block: 863552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297437 RingCT/type: yes/0
Extra: 0188c8c3e3f94310d8c22f3f91ddddd9d51de24eb4c64385ac5d4bf2f848bca69c02110000000133af99f4000000000000000000

1 output(s) for total of 0.844683058000 dcy

stealth address amount amount idx
00: 74d7f79bddbd5818922b7d8fcaab2a06d4cb403025c0a3811cf7a5cf49329818 0.844683058000 1318012 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": 863562, "vin": [ { "gen": { "height": 863552 } } ], "vout": [ { "amount": 844683058, "target": { "key": "74d7f79bddbd5818922b7d8fcaab2a06d4cb403025c0a3811cf7a5cf49329818" } } ], "extra": [ 1, 136, 200, 195, 227, 249, 67, 16, 216, 194, 47, 63, 145, 221, 221, 217, 213, 29, 226, 78, 180, 198, 67, 133, 172, 93, 75, 242, 248, 72, 188, 166, 156, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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