Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56bc3a688624d4cdfca35ec0bdce5e8ce225d126ebc8a052162a6df5713758a1

Tx prefix hash: da9cc91ec9cbe509ca3c1ab76c1254ac1134d6379dcfb3dbf8f536d5e929afab
Tx public key: 2db811aa4775d9f0f7328a1504e8ccb83807daac95a347ebf5fbbc4ede4560a5
Timestamp: 1702925836 Timestamp [UCT]: 2023-12-18 18:57:16 Age [y:d:h:m:s]: 01:149:05:47:55
Block: 916004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367809 RingCT/type: yes/0
Extra: 012db811aa4775d9f0f7328a1504e8ccb83807daac95a347ebf5fbbc4ede4560a502110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f16262e05248e6885bd0d2befc668e20e9501657c0802e784604380dccb8a2cb 0.600000000000 1373440 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": 916014, "vin": [ { "gen": { "height": 916004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f16262e05248e6885bd0d2befc668e20e9501657c0802e784604380dccb8a2cb" } } ], "extra": [ 1, 45, 184, 17, 170, 71, 117, 217, 240, 247, 50, 138, 21, 4, 232, 204, 184, 56, 7, 218, 172, 149, 163, 71, 235, 245, 251, 188, 78, 222, 69, 96, 165, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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