Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc01d871954a3b0385e9df4de67df6cb1c65e88a6faa0317eb1b94c614741108

Tx prefix hash: f08755b5f6fbf44a0635dd5bf7659e6a46eff9ce4ce63a482ccd86719c0926d0
Tx public key: 2bce459102d805aa1b913b99d516199226b8789f3e196748f0e45df59a3006c8
Timestamp: 1574728205 Timestamp [UCT]: 2019-11-26 00:30:05 Age [y:d:h:m:s]: 05:074:05:37:54
Block: 17543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1195622 RingCT/type: yes/0
Extra: 012bce459102d805aa1b913b99d516199226b8789f3e196748f0e45df59a3006c802110000000a5ce78bfa000000000000000000

1 output(s) for total of 536.875565943000 dcy

stealth address amount amount idx
00: 700fe366d7c4049d1585227d5b87c849df264f17c9ac105a1d43e5c950973637 536.875565943000 25644 of 0

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": 17553, "vin": [ { "gen": { "height": 17543 } } ], "vout": [ { "amount": 536875565943, "target": { "key": "700fe366d7c4049d1585227d5b87c849df264f17c9ac105a1d43e5c950973637" } } ], "extra": [ 1, 43, 206, 69, 145, 2, 216, 5, 170, 27, 145, 59, 153, 213, 22, 25, 146, 38, 184, 120, 159, 62, 25, 103, 72, 240, 228, 93, 245, 154, 48, 6, 200, 2, 17, 0, 0, 0, 10, 92, 231, 139, 250, 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