Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 511027411285303469f1aa84772a5e2e3389672c52b28e9c71c7384c9ca92fd6

Tx prefix hash: c6684c29a319d443daa109614ae98d52f46cb5b44a6d6eb6a98307f86dafc4c0
Tx public key: 63e1479a1d55053305da841b7a5fbcdad9bb398c728f7dc61eb7481d22c9b914
Timestamp: 1764051991 Timestamp [UCT]: 2025-11-25 06:26:31 Age [y:d:h:m:s]: 00:001:07:10:00
Block: 1419639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 928 RingCT/type: yes/0
Extra: 0163e1479a1d55053305da841b7a5fbcdad9bb398c728f7dc61eb7481d22c9b9140211000000038ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa351d6b3cf3667bad81d367f1c07d1c63f1f37e4797028956dc59acb8fe1c50 0.600000000000 1908176 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": 1419649, "vin": [ { "gen": { "height": 1419639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa351d6b3cf3667bad81d367f1c07d1c63f1f37e4797028956dc59acb8fe1c50" } } ], "extra": [ 1, 99, 225, 71, 154, 29, 85, 5, 51, 5, 218, 132, 27, 122, 95, 188, 218, 217, 187, 57, 140, 114, 143, 125, 198, 30, 183, 72, 29, 34, 201, 185, 20, 2, 17, 0, 0, 0, 3, 140, 235, 127, 9, 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