Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93ac8b5156848c2b3430379b38ec786bb33d37e4f870aa061f626dd6578b3512

Tx prefix hash: e39377017c85cb2951ef3c63f39b29e39fa7c8913ddd77ec0d42d3fa6e3f69b5
Tx public key: 01633f49e5b25571f640ddcdabec4e48b129bd0084c2b87a8d337773a0c5daae
Timestamp: 1715443096 Timestamp [UCT]: 2024-05-11 15:58:16 Age [y:d:h:m:s]: 00:227:16:27:32
Block: 1019801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162956 RingCT/type: yes/0
Extra: 0101633f49e5b25571f640ddcdabec4e48b129bd0084c2b87a8d337773a0c5daae021100000002e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0840ff049897b6f6afd2fd6e84dbf9d1cc3209d0ed5074cadc70eaf9b4c39949 0.600000000000 1483846 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": 1019811, "vin": [ { "gen": { "height": 1019801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0840ff049897b6f6afd2fd6e84dbf9d1cc3209d0ed5074cadc70eaf9b4c39949" } } ], "extra": [ 1, 1, 99, 63, 73, 229, 178, 85, 113, 246, 64, 221, 205, 171, 236, 78, 72, 177, 41, 189, 0, 132, 194, 184, 122, 141, 51, 119, 115, 160, 197, 218, 174, 2, 17, 0, 0, 0, 2, 228, 187, 107, 131, 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