Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fe8a15b7b1fc4b11ac997e75828c72b23550f16504a48be7c3e9643dbbb4e3e

Tx prefix hash: 11e028c7133fde848a4979be4047831ad7394ad152801aea121ad62f1cc2fc06
Tx public key: 4ac9ab74b13359a9f87f3c557bb51356dc0db10b45b3a0aee1c8a5bb79c99049
Timestamp: 1731262463 Timestamp [UCT]: 2024-11-10 18:14:23 Age [y:d:h:m:s]: 01:041:18:04:36
Block: 1150841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288302 RingCT/type: yes/0
Extra: 014ac9ab74b13359a9f87f3c557bb51356dc0db10b45b3a0aee1c8a5bb79c99049021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8df0b757906e1ee60aa7aac61d59795a6cdfdf32d0b6b35633721ebeb0cfdc07 0.600000000000 1636254 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": 1150851, "vin": [ { "gen": { "height": 1150841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8df0b757906e1ee60aa7aac61d59795a6cdfdf32d0b6b35633721ebeb0cfdc07" } } ], "extra": [ 1, 74, 201, 171, 116, 177, 51, 89, 169, 248, 127, 60, 85, 123, 181, 19, 86, 220, 13, 177, 11, 69, 179, 160, 174, 225, 200, 165, 187, 121, 201, 144, 73, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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