Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a767a163b83fc59f3d834d382f3b3e3dcb67f11ab41a1b09f632019863035cd

Tx prefix hash: b8b37012de56bdd24dee13e614b1a285dc4168318445ab6d201e568c83c7f590
Tx public key: f7ebf7e03748eb4dc57a6c4c84326cda7083815732829bc4cb66003e4fcdf2ea
Timestamp: 1736616120 Timestamp [UCT]: 2025-01-11 17:22:00 Age [y:d:h:m:s]: 00:083:22:08:08
Block: 1195165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59761 RingCT/type: yes/0
Extra: 01f7ebf7e03748eb4dc57a6c4c84326cda7083815732829bc4cb66003e4fcdf2ea0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 079eb8aa144c9b657bc52634cdd736fca8156ec193e417f533d96477aa688f59 0.600000000000 1681754 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": 1195175, "vin": [ { "gen": { "height": 1195165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "079eb8aa144c9b657bc52634cdd736fca8156ec193e417f533d96477aa688f59" } } ], "extra": [ 1, 247, 235, 247, 224, 55, 72, 235, 77, 197, 122, 108, 76, 132, 50, 108, 218, 112, 131, 129, 87, 50, 130, 155, 196, 203, 102, 0, 62, 79, 205, 242, 234, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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