Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbd77e60442650cc2088f7580bc451b2a7ae12c73311f3be7372cf644637984d

Tx prefix hash: 6d783f9562d4fdaf784b2bddcf1b8275a18d43f6d5428d7e9bd69529fd50f482
Tx public key: 61482c4b6060d6a12f90f7a869afc64113064e682f60ba51b75b35a0ab1e9be2
Timestamp: 1708865294 Timestamp [UCT]: 2024-02-25 12:48:14 Age [y:d:h:m:s]: 01:000:04:47:56
Block: 965249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261118 RingCT/type: yes/0
Extra: 0161482c4b6060d6a12f90f7a869afc64113064e682f60ba51b75b35a0ab1e9be20211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d5c54e99de90927e3d940bd38f3942974836f271531dc724803c6081c9cc991 0.600000000000 1424998 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": 965259, "vin": [ { "gen": { "height": 965249 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d5c54e99de90927e3d940bd38f3942974836f271531dc724803c6081c9cc991" } } ], "extra": [ 1, 97, 72, 44, 75, 96, 96, 214, 161, 47, 144, 247, 168, 105, 175, 198, 65, 19, 6, 78, 104, 47, 96, 186, 81, 183, 91, 53, 160, 171, 30, 155, 226, 2, 17, 0, 0, 0, 3, 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