Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fb898d8b6ab31df499efc0bc076bd0fe93a23b3e80d255c7472de0ad9d1c9bb

Tx prefix hash: 85caa5fce233a1f7ef19f2cae64d913acac1700d6244f1227ab8457412be9c38
Tx public key: 52bc9d3577e5e9389fde9fb4596ea3fbe94cbe07a1f5c29958e3f583a0761d9f
Timestamp: 1711370421 Timestamp [UCT]: 2024-03-25 12:40:21 Age [y:d:h:m:s]: 01:038:09:09:01
Block: 986047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288382 RingCT/type: yes/0
Extra: 0152bc9d3577e5e9389fde9fb4596ea3fbe94cbe07a1f5c29958e3f583a0761d9f0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81ae4882bbac797f3d37dea01e9e243031c0a7f4fdec49078373948009698728 0.600000000000 1446272 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": 986057, "vin": [ { "gen": { "height": 986047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81ae4882bbac797f3d37dea01e9e243031c0a7f4fdec49078373948009698728" } } ], "extra": [ 1, 82, 188, 157, 53, 119, 229, 233, 56, 159, 222, 159, 180, 89, 110, 163, 251, 233, 76, 190, 7, 161, 245, 194, 153, 88, 227, 245, 131, 160, 118, 29, 159, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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