Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71499cc8993ff9941dc18f4509ae3ae8ff0087587b55df043d7deebf3d341dd4

Tx prefix hash: bcd51fb4d0c38be9cd173ede61f2e7354e9f681f368d56e0e570690daf8c06e5
Tx public key: 8b2790cf32a903e8b92a33908712bef7f58e8201ad211db98297bba4bc1c6548
Timestamp: 1758545805 Timestamp [UCT]: 2025-09-22 12:56:45 Age [y:d:h:m:s]: 00:066:00:19:44
Block: 1374006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47270 RingCT/type: yes/0
Extra: 018b2790cf32a903e8b92a33908712bef7f58e8201ad211db98297bba4bc1c654802110000000bad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fa085999cde50f782d14ffd3e780790a4e729a6847b94e8c7eadf4e17d0ab2f 0.600000000000 1862091 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": 1374016, "vin": [ { "gen": { "height": 1374006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fa085999cde50f782d14ffd3e780790a4e729a6847b94e8c7eadf4e17d0ab2f" } } ], "extra": [ 1, 139, 39, 144, 207, 50, 169, 3, 232, 185, 42, 51, 144, 135, 18, 190, 247, 245, 142, 130, 1, 173, 33, 29, 185, 130, 151, 187, 164, 188, 28, 101, 72, 2, 17, 0, 0, 0, 11, 173, 121, 72, 208, 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