Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c52eb3c5ab75533f15c2a568d0830e792aa9e06e1a28c47e71400e6d406266c

Tx prefix hash: 1280edf7027c9e3cd7861e9a7e87425fe549a2b2deb86755178d08f915ed6846
Tx public key: ea95369ffa2956d2ace3c1e6b0635ff32e2d2402ee83893c3b6237ee4c12ceae
Timestamp: 1694882727 Timestamp [UCT]: 2023-09-16 16:45:27 Age [y:d:h:m:s]: 01:129:14:03:42
Block: 849507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353894 RingCT/type: yes/0
Extra: 01ea95369ffa2956d2ace3c1e6b0635ff32e2d2402ee83893c3b6237ee4c12ceae02110000000533af99f4000000000000000000

1 output(s) for total of 0.940222672000 dcy

stealth address amount amount idx
00: c708b3a8cf99f1f37a7cbb5473e67dafd24de1be3d178e8b920c3bd8f1acd393 0.940222672000 1303175 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": 849517, "vin": [ { "gen": { "height": 849507 } } ], "vout": [ { "amount": 940222672, "target": { "key": "c708b3a8cf99f1f37a7cbb5473e67dafd24de1be3d178e8b920c3bd8f1acd393" } } ], "extra": [ 1, 234, 149, 54, 159, 250, 41, 86, 210, 172, 227, 193, 230, 176, 99, 95, 243, 46, 45, 36, 2, 238, 131, 137, 60, 59, 98, 55, 238, 76, 18, 206, 174, 2, 17, 0, 0, 0, 5, 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