Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bef2b3f7b366bceb033de5fbfd9cafb86d6bbeee9b071c25c3e8f78de8bc2d87

Tx prefix hash: 153fdb7ae8a26f2da4cbac85e27c0e5cf5d4adfe6095b1bdd8021b086b165e59
Tx public key: 91f4eac03a9a529cac0f79f6d8067f6142ff0df87df9defd16174940ddf717e1
Timestamp: 1765929800 Timestamp [UCT]: 2025-12-17 00:03:20 Age [y:d:h:m:s]: 00:025:06:05:57
Block: 1435203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18080 RingCT/type: yes/0
Extra: 0191f4eac03a9a529cac0f79f6d8067f6142ff0df87df9defd16174940ddf717e10211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 548afd5f672d41cd8ad162e215b3d18ed716178ee192fd3e4d99cf0e9ec1aa03 0.600000000000 1924000 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": 1435213, "vin": [ { "gen": { "height": 1435203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "548afd5f672d41cd8ad162e215b3d18ed716178ee192fd3e4d99cf0e9ec1aa03" } } ], "extra": [ 1, 145, 244, 234, 192, 58, 154, 82, 156, 172, 15, 121, 246, 216, 6, 127, 97, 66, 255, 13, 248, 125, 249, 222, 253, 22, 23, 73, 64, 221, 247, 23, 225, 2, 17, 0, 0, 0, 3, 123, 30, 81, 172, 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