Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a34b93015347e1afcb0edc99b059fe3df114bde8324c19c64f06c2311af449d

Tx prefix hash: bebacd344785f36133310029c305133c0a62a0f511f88674522065ba4135ce36
Tx public key: e65f47a1386d7a3f0237a96c74463d60d470ed87e5d2a64a8ae56a65f6dfce3e
Timestamp: 1730992399 Timestamp [UCT]: 2024-11-07 15:13:19 Age [y:d:h:m:s]: 00:016:14:23:36
Block: 1148605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11874 RingCT/type: yes/0
Extra: 01e65f47a1386d7a3f0237a96c74463d60d470ed87e5d2a64a8ae56a65f6dfce3e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ca22f25fadf27742fbbfcfa40046af96ba8cdf4e0a40af9168c915e8df65194 0.600000000000 1633490 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": 1148615, "vin": [ { "gen": { "height": 1148605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ca22f25fadf27742fbbfcfa40046af96ba8cdf4e0a40af9168c915e8df65194" } } ], "extra": [ 1, 230, 95, 71, 161, 56, 109, 122, 63, 2, 55, 169, 108, 116, 70, 61, 96, 212, 112, 237, 135, 229, 210, 166, 74, 138, 229, 106, 101, 246, 223, 206, 62, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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