Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21fd10cff16d75e35fbd26396e5a1ab5b0e39ea6bebc4cac3567d8f0ef072854

Tx prefix hash: 34f36f92e8933164d4bb776cc595f2c42b34e9de30627064a1124602c3bd54c1
Tx public key: 3e59d69f4ba4d12dd59eb863082ce0789de5fdf64e9cc7978c7cbdb2bf35985f
Timestamp: 1702775659 Timestamp [UCT]: 2023-12-17 01:14:19 Age [y:d:h:m:s]: 01:161:03:09:25
Block: 914755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376330 RingCT/type: yes/0
Extra: 013e59d69f4ba4d12dd59eb863082ce0789de5fdf64e9cc7978c7cbdb2bf35985f021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b354c6c01a4fc5959262e81f0e207a14bb7de93bfdd70172ac96f54da18e958 0.600000000000 1372107 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": 914765, "vin": [ { "gen": { "height": 914755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b354c6c01a4fc5959262e81f0e207a14bb7de93bfdd70172ac96f54da18e958" } } ], "extra": [ 1, 62, 89, 214, 159, 75, 164, 209, 45, 213, 158, 184, 99, 8, 44, 224, 120, 157, 229, 253, 246, 78, 156, 199, 151, 140, 124, 189, 178, 191, 53, 152, 95, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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