Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f26f183cd2235d904a15cba0d81894115f4a1461c18c65be704b731d9c63d81a

Tx prefix hash: 0b0ed7073d5a27bd618858d04dfc47b7622db9360c9db75e9a9c9760a880a5d4
Tx public key: caf06ec3936078dface32fdf78f9b3dc256fe13c7f091698e9cac91cfd9b7649
Timestamp: 1759958855 Timestamp [UCT]: 2025-10-08 21:27:35 Age [y:d:h:m:s]: 00:035:14:23:08
Block: 1385711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25502 RingCT/type: yes/0
Extra: 01caf06ec3936078dface32fdf78f9b3dc256fe13c7f091698e9cac91cfd9b764902110000000297baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e44b7a927ea843298da0fc82dd378af905bb6f9dae5f773ca73c60cffc5530d 0.600000000000 1873874 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": 1385721, "vin": [ { "gen": { "height": 1385711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e44b7a927ea843298da0fc82dd378af905bb6f9dae5f773ca73c60cffc5530d" } } ], "extra": [ 1, 202, 240, 110, 195, 147, 96, 120, 223, 172, 227, 47, 223, 120, 249, 179, 220, 37, 111, 225, 60, 127, 9, 22, 152, 233, 202, 201, 28, 253, 155, 118, 73, 2, 17, 0, 0, 0, 2, 151, 186, 249, 34, 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