Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3918b8931557612c5759032a9d1860176fab70476d5756c596aa353957e67ff6

Tx prefix hash: 948c75939711fbad1d4a78c8c7b5e82ac91240c37789377a3f93245a705c529a
Tx public key: 05184edfdc106400dd68f9b178b8c35cfe1616ad0a4f5b1788c516529da64a59
Timestamp: 1733778193 Timestamp [UCT]: 2024-12-09 21:03:13 Age [y:d:h:m:s]: 00:335:03:50:49
Block: 1171687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237047 RingCT/type: yes/0
Extra: 0105184edfdc106400dd68f9b178b8c35cfe1616ad0a4f5b1788c516529da64a59021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f5386ea512ad8b68f8e7d3da69ee6f815417cce48c714d3b9961e34b79682d6 0.600000000000 1657474 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": 1171697, "vin": [ { "gen": { "height": 1171687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f5386ea512ad8b68f8e7d3da69ee6f815417cce48c714d3b9961e34b79682d6" } } ], "extra": [ 1, 5, 24, 78, 223, 220, 16, 100, 0, 221, 104, 249, 177, 120, 184, 195, 92, 254, 22, 22, 173, 10, 79, 91, 23, 136, 197, 22, 82, 157, 166, 74, 89, 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