Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77526c34981e9d50735fa6c73a4de07dfd299981bee8f5888ca66f0ac88888c3

Tx prefix hash: e21fc1df499e1595ba7d2b4f032a6711696bc6916b4e2961e656b920a2e7f389
Tx public key: 7499b44d448d0ac2ac5efc9fb638b3367feeebef3c92217cde9c2cfe40319bc3
Timestamp: 1737745059 Timestamp [UCT]: 2025-01-24 18:57:39 Age [y:d:h:m:s]: 00:347:03:46:13
Block: 1204472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245726 RingCT/type: yes/0
Extra: 017499b44d448d0ac2ac5efc9fb638b3367feeebef3c92217cde9c2cfe40319bc3021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33e99d69f490cfdf67f9be2292bcfdbfd92cd32eff086e87d30312ddb63d9f8a 0.600000000000 1691159 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": 1204482, "vin": [ { "gen": { "height": 1204472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33e99d69f490cfdf67f9be2292bcfdbfd92cd32eff086e87d30312ddb63d9f8a" } } ], "extra": [ 1, 116, 153, 180, 77, 68, 141, 10, 194, 172, 94, 252, 159, 182, 56, 179, 54, 127, 238, 235, 239, 60, 146, 33, 124, 222, 156, 44, 254, 64, 49, 155, 195, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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