Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6669a5c6cc504afae8b80d964b3e9100f3da400319b1279461fd1eaf3c6bfba1

Tx prefix hash: e5cfb72fe6d46ad8ae1e8c58df9ad98b9e4bc8e18f42da82c204bedc2005709c
Tx public key: 67f291537166a9f0d617405ad2d75732c8af95da8b114ffd39bb81bdeed4444e
Timestamp: 1722425068 Timestamp [UCT]: 2024-07-31 11:24:28 Age [y:d:h:m:s]: 00:252:00:25:04
Block: 1077658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180030 RingCT/type: yes/0
Extra: 0167f291537166a9f0d617405ad2d75732c8af95da8b114ffd39bb81bdeed4444e02110000000fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e510dbe8747036bff7cdcb5ae1b06ae821eede0aa0228a76aed0343b2990883 0.600000000000 1550213 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": 1077668, "vin": [ { "gen": { "height": 1077658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e510dbe8747036bff7cdcb5ae1b06ae821eede0aa0228a76aed0343b2990883" } } ], "extra": [ 1, 103, 242, 145, 83, 113, 102, 169, 240, 214, 23, 64, 90, 210, 215, 87, 50, 200, 175, 149, 218, 139, 17, 79, 253, 57, 187, 129, 189, 238, 212, 68, 78, 2, 17, 0, 0, 0, 15, 233, 20, 221, 21, 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