Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8be17b3d03491a5a47cf71e48a32487615f6c980752eeedf76bc43f407a80f72

Tx prefix hash: 23108e054ad30acd9a16bfad4067312bc95b500b93d4389473bd658f9e9d4e3e
Tx public key: 5b2cb319e8eb32b30b23c5133659b2f27e79e85333114767eb77a06ca61ccfe3
Timestamp: 1760258848 Timestamp [UCT]: 2025-10-12 08:47:28 Age [y:d:h:m:s]: 00:085:13:21:04
Block: 1388201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61281 RingCT/type: yes/0
Extra: 015b2cb319e8eb32b30b23c5133659b2f27e79e85333114767eb77a06ca61ccfe3021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3410fdf0c41e1be0b5c6f7927f3a7db50d59fb5a4a9c9d447f7a143edec7ad12 0.600000000000 1876400 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": 1388211, "vin": [ { "gen": { "height": 1388201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3410fdf0c41e1be0b5c6f7927f3a7db50d59fb5a4a9c9d447f7a143edec7ad12" } } ], "extra": [ 1, 91, 44, 179, 25, 232, 235, 50, 179, 11, 35, 197, 19, 54, 89, 178, 242, 126, 121, 232, 83, 51, 17, 71, 103, 235, 119, 160, 108, 166, 28, 207, 227, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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