Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b076e40ff74c50acd801451142f4be55c52f4984b4733ba0dc40530a8151a1cc

Tx prefix hash: 3803f981420fd8900ec7f2596608cbc0ad155f5a7b2201a0a1783d7aac6b2a5b
Tx public key: cf0ef3b89389236280bc91e46c5e11b9e62ffb7436a1d2f09072962ce15fc646
Timestamp: 1730970494 Timestamp [UCT]: 2024-11-07 09:08:14 Age [y:d:h:m:s]: 00:177:04:45:07
Block: 1148426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126482 RingCT/type: yes/0
Extra: 01cf0ef3b89389236280bc91e46c5e11b9e62ffb7436a1d2f09072962ce15fc6460211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1c864d82fdc91b85f7dbb2f9fd02354574319743c61a08e7663de63ceeafb08 0.600000000000 1633263 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": 1148436, "vin": [ { "gen": { "height": 1148426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1c864d82fdc91b85f7dbb2f9fd02354574319743c61a08e7663de63ceeafb08" } } ], "extra": [ 1, 207, 14, 243, 184, 147, 137, 35, 98, 128, 188, 145, 228, 108, 94, 17, 185, 230, 47, 251, 116, 54, 161, 210, 240, 144, 114, 150, 44, 225, 95, 198, 70, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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