Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4e120fd0b478b0005049316478465c578bcfea06654e1cb70a61597fb951f0d

Tx prefix hash: 102d9ba5d791722fb159a571f44d4889e4e98e51dab99ff18b0e405b1a9f71ca
Tx public key: 824be0b823f12589cba6fcbef7164cd0d4002bd67690a36ad11b4197c91f6e8a
Timestamp: 1719346026 Timestamp [UCT]: 2024-06-25 20:07:06 Age [y:d:h:m:s]: 00:155:22:04:52
Block: 1052123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111598 RingCT/type: yes/0
Extra: 01824be0b823f12589cba6fcbef7164cd0d4002bd67690a36ad11b4197c91f6e8a0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f4a0e3776ff1ecff37f8627a11e1b8fbb038e8279793d9a4287796aec42c2a3 0.600000000000 1522444 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": 1052133, "vin": [ { "gen": { "height": 1052123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f4a0e3776ff1ecff37f8627a11e1b8fbb038e8279793d9a4287796aec42c2a3" } } ], "extra": [ 1, 130, 75, 224, 184, 35, 241, 37, 137, 203, 166, 252, 190, 247, 22, 76, 208, 212, 0, 43, 214, 118, 144, 163, 106, 209, 27, 65, 151, 201, 31, 110, 138, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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