Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f80395fa65f505fafa2155c8e7c15651f0bd6e7f452c214f4869e4e5b3f23438

Tx prefix hash: de21cef6a9089083ba1a345418b6271eb5eda22d6b2bcb145f1bc210203a61ef
Tx public key: ea7aa91262c9d3022d289e0bb08de7ff6ffb19be83990ba2e7fe7c0f462d75b0
Timestamp: 1723828271 Timestamp [UCT]: 2024-08-16 17:11:11 Age [y:d:h:m:s]: 01:081:08:39:42
Block: 1089295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316586 RingCT/type: yes/0
Extra: 01ea7aa91262c9d3022d289e0bb08de7ff6ffb19be83990ba2e7fe7c0f462d75b002110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1a34fd36ac71705a4dc8e68f8140b07a27834aba1689aca4f504f06b0a6cabd 0.600000000000 1563914 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": 1089305, "vin": [ { "gen": { "height": 1089295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1a34fd36ac71705a4dc8e68f8140b07a27834aba1689aca4f504f06b0a6cabd" } } ], "extra": [ 1, 234, 122, 169, 18, 98, 201, 211, 2, 45, 40, 158, 11, 176, 141, 231, 255, 111, 251, 25, 190, 131, 153, 11, 162, 231, 254, 124, 15, 70, 45, 117, 176, 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