Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f26d91c7d5cb9e05e211fdf909b60d283f59846b690e8198b8c2f27cf3f80781

Tx prefix hash: cb088660c0c9e53f90af09e9a3557b45cd6a211a9f0dd9589cd904b958026170
Tx public key: 78e46e28c94906663253d08fc641aad1deaa72e8a1b13fc0723d478654b49f5f
Timestamp: 1736275125 Timestamp [UCT]: 2025-01-07 18:38:45 Age [y:d:h:m:s]: 00:297:00:31:47
Block: 1192347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209781 RingCT/type: yes/0
Extra: 0178e46e28c94906663253d08fc641aad1deaa72e8a1b13fc0723d478654b49f5f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2edf2779506f09fbf4494590e219ea51cf3d7ea793ebd04daaad1af552cab68d 0.600000000000 1678896 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": 1192357, "vin": [ { "gen": { "height": 1192347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2edf2779506f09fbf4494590e219ea51cf3d7ea793ebd04daaad1af552cab68d" } } ], "extra": [ 1, 120, 228, 110, 40, 201, 73, 6, 102, 50, 83, 208, 143, 198, 65, 170, 209, 222, 170, 114, 232, 161, 177, 63, 192, 114, 61, 71, 134, 84, 180, 159, 95, 2, 17, 0, 0, 0, 4, 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