Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23227f9eba3758a15eb8c77fdc604c119632a022a67f97752cbb685d898e5e25

Tx prefix hash: d6f84a56104a24611cb9d61bdb291ef17724f4d42741b11a7318e41c86499a13
Tx public key: 3cbca64dfd6a0003d87ab834ae963702f57305bde6c7673a3b2729d4fcb2c500
Timestamp: 1723524921 Timestamp [UCT]: 2024-08-13 04:55:21 Age [y:d:h:m:s]: 00:240:04:23:30
Block: 1086777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171539 RingCT/type: yes/0
Extra: 013cbca64dfd6a0003d87ab834ae963702f57305bde6c7673a3b2729d4fcb2c50002110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de41b745077558184812c356b92c7eb5d743cf38be4d5f848d4d2718c2d39790 0.600000000000 1561376 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": 1086787, "vin": [ { "gen": { "height": 1086777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de41b745077558184812c356b92c7eb5d743cf38be4d5f848d4d2718c2d39790" } } ], "extra": [ 1, 60, 188, 166, 77, 253, 106, 0, 3, 216, 122, 184, 52, 174, 150, 55, 2, 245, 115, 5, 189, 230, 199, 103, 58, 59, 39, 41, 212, 252, 178, 197, 0, 2, 17, 0, 0, 0, 2, 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