Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9726f30c5794f7a19d093c3d8314748d5d5860a9bf017ad84a3f051b1c1bd6a3

Tx prefix hash: b2c41b748ba29a63b16831ad19e036fabd4afa20ed4f2ae106815805bb2e0057
Tx public key: 55970521e744b6c16ac97c7f688030a9aebb4567a1f909c48764b8b96a2804a8
Timestamp: 1722244579 Timestamp [UCT]: 2024-07-29 09:16:19 Age [y:d:h:m:s]: 00:250:00:17:55
Block: 1076169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178582 RingCT/type: yes/0
Extra: 0155970521e744b6c16ac97c7f688030a9aebb4567a1f909c48764b8b96a2804a8021100000003b6cd74da000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 086ab2b7fa47deda2bfa392a663bf4c385b610b1ea842e5d65730daf2acd3005 0.600000000000 1548704 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": 1076179, "vin": [ { "gen": { "height": 1076169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "086ab2b7fa47deda2bfa392a663bf4c385b610b1ea842e5d65730daf2acd3005" } } ], "extra": [ 1, 85, 151, 5, 33, 231, 68, 182, 193, 106, 201, 124, 127, 104, 128, 48, 169, 174, 187, 69, 103, 161, 249, 9, 196, 135, 100, 184, 185, 106, 40, 4, 168, 2, 17, 0, 0, 0, 3, 182, 205, 116, 218, 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