Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e1232cb001b73802e98657bcdb4345dcf8203bfc15377fb1e006f2e17a72551

Tx prefix hash: b9fff078b8802c3ea49e314afab61c2ddfd25d40d6c95c2c5a8f2302de31eb59
Tx public key: d979b24cce06e64a956b3a68da1aca4731e5fcbe2d6b0eb6b888d7c346603c9e
Timestamp: 1715964509 Timestamp [UCT]: 2024-05-17 16:48:29 Age [y:d:h:m:s]: 00:251:05:23:41
Block: 1024104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179750 RingCT/type: yes/0
Extra: 01d979b24cce06e64a956b3a68da1aca4731e5fcbe2d6b0eb6b888d7c346603c9e0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3d40c83d26f3251c651e2c2848165503be4cc1d945d3ad9a5e10f2c0b255656 0.600000000000 1489587 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": 1024114, "vin": [ { "gen": { "height": 1024104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3d40c83d26f3251c651e2c2848165503be4cc1d945d3ad9a5e10f2c0b255656" } } ], "extra": [ 1, 217, 121, 178, 76, 206, 6, 230, 74, 149, 107, 58, 104, 218, 26, 202, 71, 49, 229, 252, 190, 45, 107, 14, 182, 184, 136, 215, 195, 70, 96, 60, 158, 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