Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8aa18ebd2667feff893baa6945863d293eab6caec009ead0ce8e3b87777a9cc

Tx prefix hash: 99f440207ee4e7a4e34f500b10dd7e334ae369f518eabc1ccf3d459b42dd0a63
Tx public key: 33559e234c61fab96f848b32fe55978f33524fe234c9aee048ba00beb84a8502
Timestamp: 1699748903 Timestamp [UCT]: 2023-11-12 00:28:23 Age [y:d:h:m:s]: 01:142:23:16:32
Block: 889664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363354 RingCT/type: yes/0
Extra: 0133559e234c61fab96f848b32fe55978f33524fe234c9aee048ba00beb84a85020211000000024b8f5122000000000000000000

1 output(s) for total of 0.692107968000 dcy

stealth address amount amount idx
00: 32d33a90237c9ffbfa0ec356fd376cc1ca370d441e0a1bf4df7728bc2dbb1bc9 0.692107968000 1345673 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": 889674, "vin": [ { "gen": { "height": 889664 } } ], "vout": [ { "amount": 692107968, "target": { "key": "32d33a90237c9ffbfa0ec356fd376cc1ca370d441e0a1bf4df7728bc2dbb1bc9" } } ], "extra": [ 1, 51, 85, 158, 35, 76, 97, 250, 185, 111, 132, 139, 50, 254, 85, 151, 143, 51, 82, 79, 226, 52, 201, 174, 224, 72, 186, 0, 190, 184, 74, 133, 2, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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