Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ef0f3d4306296848e30dec799e9f62552ab202e8687d2bd6a227c73fb4523c6

Tx prefix hash: f47221612d85cc1ed0d2a534c263a6422629c8c501883df06b6e710593eec74d
Tx public key: 074d65a8f7854bf90b73d5cd5a132c9b7a4dd7936d097b1b905bbe86c508760a
Timestamp: 1761628299 Timestamp [UCT]: 2025-10-28 05:11:39 Age [y:d:h:m:s]: 00:031:01:53:53
Block: 1399563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22243 RingCT/type: yes/0
Extra: 01074d65a8f7854bf90b73d5cd5a132c9b7a4dd7936d097b1b905bbe86c508760a02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37b9c42d3cf1d4704241bf63cf0043b463de253d9f7cd3989112d647b4644a5c 0.600000000000 1887868 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": 1399573, "vin": [ { "gen": { "height": 1399563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37b9c42d3cf1d4704241bf63cf0043b463de253d9f7cd3989112d647b4644a5c" } } ], "extra": [ 1, 7, 77, 101, 168, 247, 133, 75, 249, 11, 115, 213, 205, 90, 19, 44, 155, 122, 77, 215, 147, 109, 9, 123, 27, 144, 91, 190, 134, 197, 8, 118, 10, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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