Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 135742534bcc5fd78023e08ee9a3c15527e1848be16aac2fd7240edc1b3e5263

Tx prefix hash: dd3aeaeb3f19ff5b74ed310fb3dd69cc019b55ef67c92b3c0c0248d59f2eb416
Tx public key: 1bf4dccaae3f7767e7663fdba23cadbdd9a9197aed1022bfea5f94515bd11a30
Timestamp: 1711959808 Timestamp [UCT]: 2024-04-01 08:23:28 Age [y:d:h:m:s]: 01:053:01:40:20
Block: 990864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298962 RingCT/type: yes/0
Extra: 011bf4dccaae3f7767e7663fdba23cadbdd9a9197aed1022bfea5f94515bd11a3002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eadb6cc9f1255a3c1deffe43cc6de41ea1d71c0e775f8dd5ba206836428341a4 0.600000000000 1451196 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": 990874, "vin": [ { "gen": { "height": 990864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eadb6cc9f1255a3c1deffe43cc6de41ea1d71c0e775f8dd5ba206836428341a4" } } ], "extra": [ 1, 27, 244, 220, 202, 174, 63, 119, 103, 231, 102, 63, 219, 162, 60, 173, 189, 217, 169, 25, 122, 237, 16, 34, 191, 234, 95, 148, 81, 91, 209, 26, 48, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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