Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab2fdcbd728fdf725e1e26983086d8eb70c0b91fdb2c00935d3fa00a032489ff

Tx prefix hash: 1d7490a949dd8a07bbd6904273d6e77d803563ee23f286cc17c346e367e7c563
Tx public key: 1bcde6c04da20a8bcca42915b914435d5fd55193ed9dbea20d1f0c51bcb6568e
Timestamp: 1737292350 Timestamp [UCT]: 2025-01-19 13:12:30 Age [y:d:h:m:s]: 00:149:03:31:53
Block: 1200726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106346 RingCT/type: yes/0
Extra: 011bcde6c04da20a8bcca42915b914435d5fd55193ed9dbea20d1f0c51bcb6568e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16a13c695b4a87f62b34385c844a4ee978e1924966e1072811082b5fa1a66c06 0.600000000000 1687371 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": 1200736, "vin": [ { "gen": { "height": 1200726 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16a13c695b4a87f62b34385c844a4ee978e1924966e1072811082b5fa1a66c06" } } ], "extra": [ 1, 27, 205, 230, 192, 77, 162, 10, 139, 204, 164, 41, 21, 185, 20, 67, 93, 95, 213, 81, 147, 237, 157, 190, 162, 13, 31, 12, 81, 188, 182, 86, 142, 2, 17, 0, 0, 0, 2, 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