Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e52ea20c8b20487bb694c40e3efbc86a17012594c31c2ee564b471e1ec555f1c

Tx prefix hash: ca77452eaa90d3eeae6f9380ebd8f92d6b5b590308434b828161cc0a342234b9
Tx public key: 4e56b0d08c35825e438ea56df66c318bd01ba54535bb415b5fc37573f865fdc4
Timestamp: 1726657104 Timestamp [UCT]: 2024-09-18 10:58:24 Age [y:d:h:m:s]: 00:212:21:14:21
Block: 1112746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151982 RingCT/type: yes/0
Extra: 014e56b0d08c35825e438ea56df66c318bd01ba54535bb415b5fc37573f865fdc402110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8480d6efa621ddb5d1ab3b919aa9c279666616dc5b7e85792a5047687b749e6 0.600000000000 1592173 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": 1112756, "vin": [ { "gen": { "height": 1112746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8480d6efa621ddb5d1ab3b919aa9c279666616dc5b7e85792a5047687b749e6" } } ], "extra": [ 1, 78, 86, 176, 208, 140, 53, 130, 94, 67, 142, 165, 109, 246, 108, 49, 139, 208, 27, 165, 69, 53, 187, 65, 91, 95, 195, 117, 115, 248, 101, 253, 196, 2, 17, 0, 0, 0, 7, 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