Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 480dfe71b457661f8d092ccffde28534a6a09b17fa401860c2c694879bb8aea6

Tx prefix hash: 33791bd839d2b50b91c8de1ac90f52087c478f21f754581cc64270c8b47c1b10
Tx public key: c675cba6e5d4896ff76f8a6ffd87a5e0923f5d8169434feddc62c162a7316268
Timestamp: 1719076749 Timestamp [UCT]: 2024-06-22 17:19:09 Age [y:d:h:m:s]: 00:299:21:28:21
Block: 1049885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214329 RingCT/type: yes/0
Extra: 01c675cba6e5d4896ff76f8a6ffd87a5e0923f5d8169434feddc62c162a73162680211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d35a26f1f20346d8e642dd2fa7678dd242630264544152abb7f1cd4c20c6a3b4 0.600000000000 1519990 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": 1049895, "vin": [ { "gen": { "height": 1049885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d35a26f1f20346d8e642dd2fa7678dd242630264544152abb7f1cd4c20c6a3b4" } } ], "extra": [ 1, 198, 117, 203, 166, 229, 212, 137, 111, 247, 111, 138, 111, 253, 135, 165, 224, 146, 63, 93, 129, 105, 67, 79, 237, 220, 98, 193, 98, 167, 49, 98, 104, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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