Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d38fffe2d86294565fb42c6cf1ddc7e241b148f810179377043526d8a7d8bf25

Tx prefix hash: 7a93173adc7ea3f87cf7512c351db83e7bb2dd137c044158d705a90e57097867
Tx public key: 8cbd4b8f2d9276466eee2bf2983b17ee2be498f0e3cc1e816a3d121d4dce01c5
Timestamp: 1764560107 Timestamp [UCT]: 2025-12-01 03:35:07 Age [y:d:h:m:s]: 00:002:23:12:54
Block: 1423854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2118 RingCT/type: yes/0
Extra: 018cbd4b8f2d9276466eee2bf2983b17ee2be498f0e3cc1e816a3d121d4dce01c5021100000001fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c92f7f03b901015c949056b54ce38e12bc7fd5cda0dd89c7366f15a4ba667008 0.600000000000 1912481 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": 1423864, "vin": [ { "gen": { "height": 1423854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c92f7f03b901015c949056b54ce38e12bc7fd5cda0dd89c7366f15a4ba667008" } } ], "extra": [ 1, 140, 189, 75, 143, 45, 146, 118, 70, 110, 238, 43, 242, 152, 59, 23, 238, 43, 228, 152, 240, 227, 204, 30, 129, 106, 61, 18, 29, 77, 206, 1, 197, 2, 17, 0, 0, 0, 1, 251, 143, 208, 137, 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