Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd73b3221b7e7611af82235ef4b6082310bcba5dacb95d810bf37ae3115c440a

Tx prefix hash: 772a5c35a6d4f3a1f629438cc673298aab1277dc254f39f32e8d194228c7c49c
Tx public key: ab443fbe145db9a8ee67e1c77f7821d50bd7efcfcb1103acf3d521e569bfb127
Timestamp: 1752329769 Timestamp [UCT]: 2025-07-12 14:16:09 Age [y:d:h:m:s]: 00:132:07:01:05
Block: 1323958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93256 RingCT/type: yes/0
Extra: 01ab443fbe145db9a8ee67e1c77f7821d50bd7efcfcb1103acf3d521e569bfb1270211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b543551a56c3fd7821d8aa8ecf17d95d99ffe74dea8ea33a5fd7f80d6e279f4 0.600000000000 1811699 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": 1323968, "vin": [ { "gen": { "height": 1323958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b543551a56c3fd7821d8aa8ecf17d95d99ffe74dea8ea33a5fd7f80d6e279f4" } } ], "extra": [ 1, 171, 68, 63, 190, 20, 93, 185, 168, 238, 103, 225, 199, 127, 120, 33, 213, 11, 215, 239, 207, 203, 17, 3, 172, 243, 213, 33, 229, 105, 191, 177, 39, 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