Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed25b14ff87cb1c802f1359ebe57625f1f81444bbbfd3189dc6ae6a0776d0cbf

Tx prefix hash: a4b3d40150d11216f7f3c52103bb7c8f382e3c43f4987d907e13186d5b3a5c93
Tx public key: fe960bf68c93a8949adceff2f8a6a666d7da37701272f3fe3bc7644cfdecbace
Timestamp: 1705148598 Timestamp [UCT]: 2024-01-13 12:23:18 Age [y:d:h:m:s]: 01:082:03:06:16
Block: 934417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319803 RingCT/type: yes/0
Extra: 01fe960bf68c93a8949adceff2f8a6a666d7da37701272f3fe3bc7644cfdecbace02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cc93f9709af5963380b226bc05eb3e8d75fe994ed43d19433aea96c2e44d3e2 0.600000000000 1392425 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": 934427, "vin": [ { "gen": { "height": 934417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cc93f9709af5963380b226bc05eb3e8d75fe994ed43d19433aea96c2e44d3e2" } } ], "extra": [ 1, 254, 150, 11, 246, 140, 147, 168, 148, 154, 220, 239, 242, 248, 166, 166, 102, 215, 218, 55, 112, 18, 114, 243, 254, 59, 199, 100, 76, 253, 236, 186, 206, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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