Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa507fbdd2617878cad5835aaf8e4ff64e34409993dcf5bb8b1407f1bcd898c4

Tx prefix hash: 4e89776f6cb2901d81eb7ba50d2275a2c520b544cac3fe91bc91664679672626
Tx public key: ff4000e387b3f1e1aea091568889a65f99a6e51a33d3f19f2762804e39d11756
Timestamp: 1745850916 Timestamp [UCT]: 2025-04-28 14:35:16 Age [y:d:h:m:s]: 00:252:05:45:27
Block: 1271365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178064 RingCT/type: yes/0
Extra: 01ff4000e387b3f1e1aea091568889a65f99a6e51a33d3f19f2762804e39d1175602110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3c8e2b8c5a64b3d645288c83ffdb503be67d36e6f5601d0c876c3fd7eab5011 0.600000000000 1758626 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": 1271375, "vin": [ { "gen": { "height": 1271365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3c8e2b8c5a64b3d645288c83ffdb503be67d36e6f5601d0c876c3fd7eab5011" } } ], "extra": [ 1, 255, 64, 0, 227, 135, 179, 241, 225, 174, 160, 145, 86, 136, 137, 166, 95, 153, 166, 229, 26, 51, 211, 241, 159, 39, 98, 128, 78, 57, 209, 23, 86, 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